-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix!: Fix pagination support for IssuesService list methods
#3984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix!: Fix pagination support for IssuesService list methods
#3984
Conversation
|
@gmlewis, @alexandear and @Not-Dhananjay-Mishra can you please review this PR? |
IssuesService list methods
IssuesService list methodsIssuesService list methods
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3984 +/- ##
==========================================
- Coverage 93.52% 93.52% -0.01%
==========================================
Files 207 207
Lines 17593 17592 -1
==========================================
- Hits 16454 16453 -1
Misses 938 938
Partials 201 201 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
gmlewis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @maishivamhoo123!
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.
cc: @stevehipwell - @alexandear - @zyfy29 - @Not-Dhananjay-Mishra
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also SubIssueService.ListByIssue ( Point 3 in #3976 ) also accepts IssueListOptions as one of the parameters so we can also include that in BREAKING CHANGE description
|
|
||
| // Add ListOptions so offset pagination with integer type "page" query parameter is accepted | ||
| // since ListCursorOptions accepts "page" as string only. | ||
| ListOptions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't remove ListOptions. keep both (only for IssueListByRepoOptions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Not-Dhananjay-Mishra - so are you saying that this PR should be completely closed since both iteration options are needed?
Or are you saying that this struct (IssueListOptions) needs to be split up for different methods?
Looking through this PR now, I'm seeing that this remove here of ListOptions is essentially the only breaking change, right?
How should we proceed with this one?
gmlewis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @maishivamhoo123!
when i am removing the pointer from
}` |
|
@maishivamhoo123 Lines 290 to 294 in e5024aa
|
OK, this is my fault for flip-flopping on my opinions about struct tags and pointers. |
now everything is working fine Sir? can you please review the pr? |

BREAKING CHANGE:
ListCursorOptionsis removed fromIssuesService.ListandIssuesService.ListByRepo.Updates: #3976.
Removed unsupported cursor pagination IssuesService.List and IssuesService.ListByRepo by deleting ListCursorOptions from issue option structs. Updated related unit tests accordingly.